-
Notifications
You must be signed in to change notification settings - Fork 379
test: expand assert_no_critical_errors to also allow checking other metrics + add a default check in system tests that no consensus artifacts were invalidated
#8815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
basvandijk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. LGTM!
eichhorl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively it could be checked by default with an option to disable it?
Good idea, let me do that |
|
@basvandijk @eichhorl @pierugo-dfinity |
assert_no_critical_errors to also allow checking other metrics + add a check to several consensus system tests that no artifacts where invalidatedassert_no_critical_errors to also allow checking other metrics + add a default check in system tests that no consensus artifacts where invalidated
assert_no_critical_errors to also allow checking other metrics + add a default check in system tests that no consensus artifacts where invalidatedassert_no_critical_errors to also allow checking other metrics + add a default check in system tests that no consensus artifacts were invalidated
Failing test output example: